Repository navigation
feat(api): budget sponsorship in self-hosted deployments too - #2582
Closed
multipletwigs wants to merge 4 commits into
Closed
multipletwigs wants to merge 4 commits into
multipletwigs wants to merge 4 commits into
Conversation
Contributor
 [High impact] The PR appears safe to merge, with no new blocking issues found. SummarySelf-hosted sponsorship now uses
No new actionable issues were found in the changes since the previous review. multipletwigs manually resolved the earlier test-coverage thread without an explanatory reply. Reviews (4) · Last reviewed commit: "test(web): clear sponsorship reservation..." · Reviewed by Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
multipletwigs
force-pushed
the
chore/sponsorship-budget-self-hosted
branch
from
October 27, 2026 14:15
41a7747 to
503361b
Compare
createSponsorshipFeePayment always returns the budgeted fee payment, so self-hosted operators get the same per-project and global caps, breaker and reconciliation as managed SDP, and local runs exercise the production path. Redis and Kora's RPC were already required at boot in every mode.
… the Surfpool shim The shim advertised 10,000,000 lamports while infra/kora/kora.toml allows 9,900,000. With self-hosted runs now budgeted, the worst-case reservation (network fee plus max_allowed_lamports) exceeded the sandbox per-transaction cap and every sponsored call returned 429.
multipletwigs
force-pushed
the
chore/sponsorship-budget-self-hosted
branch
from
October 27, 2026 14:22
503361b to
5b0742b
Compare
…organizations Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QhoeJoQRZxzdNUMVTZXeoU
Contributor
|
React Doctor found no new issues. 🎉 Reviewed by React Doctor for commit |
Collaborator
Author
|
backoffice solves this |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #2580. Self-hosted deployments now sponsor through the same budget as managed SDP:
createSponsorshipFeePaymentalways returnsBudgetedFeePayment.withOwnedSubmissionLifecycle), so self-hosted operators get the per-project and global caps, breaker and reconciliation by default, and local runs exercise the production path without KMS.KORA_<CLUSTER>_RPC_URL) were already required at boot in every mode.Verification: typecheck 28/28, biome clean. Against the local
self_hostedstack with devnet Kora, a sponsored transfer reserved the worst case (9,910,000 lamports) againstglobalandproject:<id>and settled to the actual 10,000. A 1,000-lamport project cap refused and released; a missing project row refused only that project with the breaker closed; kill refused and resume restored. Vitest not run locally.Known gap, not changed here: a budget refusal on
POST /v1/payments/transferssurfaces as502 SOLANA_RPC_ERRORwith the internal message, becausemapTransferExecutionErroronly passesAppErrorthrough.